chore(deps-dev): bump replace-in-file from 7.2.0 to 8.4.0 - #150

Sourced from replace-in-file's changelog.

8.0.0

The package has been converted to an ES module and now requires Node 18 or higher. If you need support for Node 16 or below, please use version 7.x.x.

Breaking changes

• Package has been converted to an ES module
• No longer providing a default export. Use the named exports replaceInFile or replaceInFileSync instead.
• The replace.sync syntax is no longer available. Use the named export replaceInFileSync instead.
• The callback API has been removed for asynchronous replacements. Please use promises or async/await instead.
• Configuration files provided to the CLI using the --configFile flag can now only be JSON.
• To use a custom fs implementation, you must now specify fs config parameter for the async API, and fsSync for the sync API. For the asynchronous APIs, the provided fs must provide the readFile and writeFile methods. For the synchronous APIs, the provided fsSync must provide the readFileSync and writeFileSync methods.
• If a cwd parameter is provided, it will no longer be prefixed to each path using basic string concatenation, but rather uses path.join() to ensure correct path concatenation.

New features

• The isRegex flag is no longer required.
• You can now specify a getTargetFile config param to modify the target file for saving the new file contents to. For example:

const options = {
  files: 'path/to/files/*.html',
  getTargetFile: source => `new/path/${source}`,
  from: 'foo',
  to: 'bar',
}

7.0.0

Strings provided to the from value are now escaped for regex matching when counting of matches is enabled. This is unlikely to result in any breaking changes, but as a precaution the major version has been bumped.

6.0.0

From version 6.0.0 onwards, replace in file requires Node 10 or higher. If you need support for Node 8, please use version 5.x.x.

5.0.0

From version 5.0.0 onwards, replace in file requires Node 8 or higher. If you need support for Node 6, please use version 4.x.x.

4.0.0

Breaking changes

The return value is now a results array instead of an array with changed files. The new results array includes each file that was processed, with a flag to indicate whether or not the file was changed, and optionally information about the number of matches and replacements that were made. See the readme for more details.

To update existing code and obtain an array of changed files again, simply convert the results array as follows:

const results = await replace(options);
const changedFiles = results
  .filter(result => result.hasChanged)
  .map(result => result.file);

... (truncated)

• 2f30a81 Use files directive in package.json
• 57320d0 Upgrade all dependencies
• 6e42200 Bump cross-spawn from 7.0.3 to 7.0.6 (#203)
• e9f4f16 Update package.json
• 4ae6ac9 feat: initial implementation of processorAsync (#205)
• 5e33265 fix: missing getTargetFile type (#206)
• fc5af6d Fix #199 – Allow regexes in array
• 8d77abc Update README.md
• d0b8c0d [fix] $168 Add help command to CLI
• dc5e8cd [fx] #197 , remove need for regex flag
• Additional commits viewable in compare view